-
Notifications
You must be signed in to change notification settings - Fork 279
Allow selecting new problem types as part of the problem entity. #2979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
8289465
to
9251876
Compare
570510e
to
4d6d542
Compare
While you can select the new types, they won't function yet. Part of DOMjudge#2525 Problem types are defined here: https://icpc.io/problem-package-format/spec/2023-07-draft.html#type
if (!($this->types & self::TYPE_PASS_FAIL) xor ($this->types & self::TYPE_SCORING)) { | ||
throw new Exception("Invalid problem type: must be exactly one of 'pass-fail' or 'scoring'."); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that pass-fail
is implied when it is not provided. For example, type: interactive
implies type: [pass-fail, interactive]
. I noticed this when doing a test upload today 😂
See also: Kattis/problem-package-format#440
EDIT: Looks like this was fixed in 2b7adab
(#2999), thanks! ❤️
It's now also in the spec, see Kattis/problem-package-format#471 😄
While you can select the new types, they won't function yet.
Part of #2525
Problem types are defined here: https://icpc.io/problem-package-format/spec/2023-07-draft.html#type